<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) 2022 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta http-equiv="Content-Style-Type" content="text/css">
<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
<title>Eclipse 4.28 Plug-in Migration Guide</title>
</head>

<body>

<h1>Eclipse 4.28 Plug-in Migration Guide</h1>
<p>This guide covers migrating Eclipse 4.27 plug-ins to Eclipse 4.28.</p>
<p>One of the goals of Eclipse 4.28 was to move Eclipse forward while remaining compatible
  with previous versions to the greatest extent possible. That is, plug-ins written
  against the Eclipse 4.27 APIs should continue to work in 4.28 in spite of any API changes.</p>
<p>The key kinds of compatibility are API contract compatibility and binary compatibility.
  API contract compatibility means that valid use of 4.27 APIs remains valid for
  4.28, so there is no need to revisit working code. Binary compatibility means
  that the API method signatures, etc. did not change in ways that would cause
  existing compiled (&quot;binary&quot;) code to no longer link and run with the
  new 4.28 libraries.</p>
<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
  APIs that should be adopted by clients.
  This document describes those areas and provides instructions for migrating 4.27 plug-ins to
  4.28.</p>
<ul>
  <li><a href="4.28/faq.html">Eclipse 4.28 Plug-in Migration FAQ</a></li>
  <li><a href="4.28/incompatibilities.html">Incompatibilities between Eclipse 4.27 and 4.28</a></li>
  <li><a href="4.28/recommended.html">Adopting 4.28 mechanisms and API</a></li>
</ul>

</body>
</html>
